Investigate Appveyor alternatives for more parallel builds: Github Actions; Travis; CircleCI #4131
Comments
|
Xref #4549 where we almost certainly need to migrate from Travis rather urgently: and Appveyor is a possibility, in a reversal of this issue. |
|
Assigning to me since I started some work on Dr. Memory's Windows CI on Github Actions which overlaps with the work for DR: DynamoRIO/drmemory#2326 |
|
If we successfully add auto-cancellation (#4585) to Github Actions that could be another big reason to move from Appveyor, avoiding the current pain: https://github.com/DynamoRIO/dynamorio/wiki/Test-Suite#ci-resources-and-appveyor-global-serialization |
Adds two separate jobs on Windows, 32-bit and 64-bit. We target a VS2017 Win10-1607 image to match what we had on Appveyor. Modifies the runsuite_wrapper.pl script to *not* fork, since there is no Cygwin perl available by default. Instead, we tee to a file. This is based on the similar work in progress for Dr. Memory: DynamoRIO/drmemory#23 Issue: #4131
Adds three separate jobs on Windows: 32-bit debug with tests, 64-bit debug with tests, and a job that creates 3 builds without tests: release-32, release-64, and vps-32-debug. Adds corresponding flags to the script layers to accomplish this build splitting. We target a VS2017 Win10-1607 image to match what we had on Appveyor. Modifies the runsuite_wrapper.pl script to *not* fork, since there is no Cygwin perl available by default. Instead, we tee to a file. Updates checks for Cygwin to apply to native Windows perl as well. Includes attempts to improve two tests: + Add error code printing for drx-test + Generalize api.symtest golden output to handle extra operators found Other failing tests were either already on the ignore list or we add them here. The long list of tests ignored for #4058 is culled to remove tests never observed to fail on GA. Removes APPVEYOR_PULL_REQUEST_NUMBER-driven build skips now that we have a separate build job. Sets a CI_TRIGGER env var and use it to shrink 32-bit tests in the same manner as before for Appveyor PR runs. This is based on the similar work for Dr. Memory: DynamoRIO/drmemory#2326 Issue: #4131
|
I removed the Appveyor webhook and swapped to the GA jobs as the ones that are required to merge. |
Now that we have switched our Windows CI to Github Actions we no longer need an Appveyor config file. Issue: #4131
|
We now have every single CI job under ~15 mins (64-bit Windows is sometimes 16 mins or so). It's pretty nice. Add in no serialization across PR's or repos, and auto-cancellation of prior jobs, and it's really nice. Unfortunately there are still a number of tests failing on Windows which are just on an ignore list, but that's how it was with Appveyor when we moved to Win10 VS2017. Hopefully someone will get some time to fix a few of them. I think it would be best to file separate issues instead of lumping them all under here or #4058 so I will take that as an action item to file them all separately (the set failing on GA is slightly different from Appveyor). |
Now that we have switched our Windows CI to Github Actions we no longer need an Appveyor config file. Issue: #4131
|
#4619 also. |
Updates the Windows CI ignore list bug numbers to reflect the newly-filed individual issues. Re-adds client.drwrap-test-detach to the ignore list for 32-bit, and adds histogram-offline to 64-bit (both were already there for the other bitwidth). Issue: #2246, #4616, #4617, #4618, #4619, #4621, #4622, #4131, #4058
Appveyor's big downside is the single sequential job serialized across both dynamorio and drmemory repositories and across PR's and master merges. One single job is now down to ~23-24 mins thanks to #4059 which is not that different from a Travis invocation, but the lack of parallelism does cause pain.
Possible alternatives that now include Windows (all quite recently):
The text was updated successfully, but these errors were encountered: