try: -b do -p all -u all -t none draft
authorISHIKAWA, Chiaki <ishikawa@yk.rim.or.jp>
Mon, 23 May 2022 03:04:10 +0900
changeset 116841 beaacca97fbd493b51fe56d411c62ebfaeab6467
parent 116840 1c6c88c74c912d69723595827bcf30bf3f90cfaa
push id15955
push userishikawa@yk.rim.or.jp
push dateSun, 22 May 2022 18:04:18 +0000
treeherdertry-comm-central@beaacca97fbd [default view] [failures only]
try: -b do -p all -u all -t none Maybe I should simply say all for -p? # took out macosx64 configuration error on build farm try: -b do -p linux64,macosx64,win64,win32 -u all -t none try: -b do -p linux64 -u all -t none # for testing the mDatabase patch # During testing of linux64 and Win32 # try: -b do -p linux64,win32 -u all -t none # try: -b do -p linux64,macosx64,win64,win32 -u all -t none # ??? try: -b do -p linux64,macosx64 -u all -t none # Had to take out win32 since it seems to cause breakage. Oct 31, 2019 # There was an issue that was handled. try: -b do -p linux64,macosx64,win64,win32 -u all -t none # Had to take out win32 since it seems to cause breakage. Oct 31, 2019 # 2019, July 12: Now I have to say -u all to run mozmill along with others... # It was "try: -b do -p linux64,macosx64,win64,win32 -u xpcshell,mozmill -t none" # removed --buildbot in Aug 2018. buildbot is dead. # added --buildbot in Jan 2018 # patches-saved-broken-2019-10-10-FORMAT replaced by the current patch queue name by script magic # linux64-valgrind does not seem to work on try-comm-central # try: -b d -p linux64-valgrind -u none -t none # try: -b do -p win64,win32 -u xpcshell,mozmill -t none # windows only # the following did not run any win build!? -b do -p linux64,macosx64,win64,win32 -u xpcshell[x64,10.10,Windows 8],mozmill[x64,10.10,Windows 8] -t none[x64,10.10,Windows 8] cf. linux is for 32-bit. linux64 is for 64-bit. macosx64 also.