ee4dfe922f
Allow authority to be specified in check-pr ( #1473 )
...
* fix interactive login in check-pr
* specify tenant domain in check-pr
* bug fix
* rename tenant to authority
2022-02-02 16:06:42 -08:00
d358938895
Working in retry to test endpoint during integration test. ( #1565 )
2022-01-27 11:00:22 -08:00
1de2cc841d
Check-pr creates and uses SP. ( #1504 )
...
* Check-pr creates and uses SP.
* flake8.
* flake8.
* Fixing var name.
* Fixing deploy.py
* Looking for client_secret
* Change to check_output.
* mypy fix.
* Fixing check-pr
* working version.
* lint
* Updating arg text.
* Removing redundant functionality.
* Changing register codepath and adding flag.
* Removing pycache file.
* Fixing unattended flag.
* Adding space.
* Fixing a few calls.
* Removing file.
* Removing python3.
* Removing old file.
* Adding wait into registration.py
* Formatting registration.py.
* Removing space.
* Adding retry logic to check-pr.
* Formatting.
* Retriggering.
* Retriggering.
* Calling sp_create and adding retry to authorize.
* Fixing syntax.
* Removing comments.
* Adding another retry.
* Retriggering.
* Retriggering.
* Retriggering.
* Trying to find error.
* Adding retry logic.
* Increasing sleep.
* Fixing formatting.
* Retriggering.
* Removing bad file.
* Trying out retry for logger.
* typevar issue?
* Re-adding.
* Retriggering.
* retriggering.
* Retriggering.
Co-authored-by: nharper285 <nharper285@gmail.com >
Co-authored-by: Cheick Keita <kcheick@gmail.com >
2021-12-17 09:44:04 -08:00
09bdad4979
work around issues between released version of cargo-fuzz and nightly ( #1284 )
...
See rust-fuzz/cargo-fuzz#276
Co-authored-by: Brian Caswell <bmc@shmoo.com >
2021-09-27 11:29:31 -04:00
9413377c90
handle fake crash reports generated by debugging tools in regression tasks ( #1233 )
2021-09-22 17:16:35 +00:00
041d3cc204
ignore table exists errors from integration testing at the azure functions layer ( #1096 )
2021-07-21 13:29:13 -04:00
e065b571f7
add format string bug to example integration test ( #1087 )
2021-07-20 05:00:45 -04:00
3305732160
increase libfuzzer integration test -runs ( #1081 )
2021-07-16 17:29:37 -04:00
1121ebc6e8
fix issue specifying target_options for libfuzzer targets ( #1066 )
2021-07-14 14:38:35 -04:00
b9950c5526
update log messages to ease debugging ( #988 )
2021-06-14 15:18:03 -04:00
cf3d904940
address formatting from black 21.4b0 ( #831 )
2021-04-26 12:35:16 -04:00
794400adf1
ignore benign error messages when checking integration test logs ( #775 )
2021-04-06 15:35:54 -04:00
ca12904684
add log checking to refactored integration check ( #700 )
...
In practice, Application Insights can take up to 3 minutes before something sent to it is available via KQL.
This PR logs a start and stop marker such that the integration tests only search for logs during the integration tests. This reduces the complexity when using the integration tests during the development process.
Note: this migrated the new functionality from #356 into the latest integration test tools.
2021-04-02 21:49:19 +00:00
2417c37a60
add LoadLibrary integration test ( #689 )
2021-03-19 09:46:26 -04:00
6e60a8cf10
add regression testing tasks ( #664 )
2021-03-18 15:37:19 -04:00
f41f110af8
libfuzzer library integration tests ( #681 )
2021-03-17 16:18:10 -04:00
f6a426cc07
enable long-running integration tests ( #654 )
2021-03-10 17:03:15 -05:00
7fc725d012
add non-x86_64 architecture libfuzzer target support using qemu-user ( #600 )
2021-03-03 19:06:50 -05:00
cc5965ebbf
add .gitignore to ignore libfuzzer-dotnet build artifacts ( #564 )
2021-02-19 09:32:26 +00:00
f64a0dcc05
lint integration-test.py ( #549 )
2021-02-16 12:22:45 -05:00
933fe6850c
libfuzzer-dotnet integration ( #535 )
2021-02-11 17:30:24 -05:00
4f941d5ff2
add the task_id to the integration failure logs ( #446 )
2021-01-21 13:35:54 -05:00
af2ef9f4fa
verify local debugger installs before launching repro ( #436 )
...
This only launches the repro test cases if you have the os-specific prerequisite debugger installed.
2021-01-18 23:30:53 +00:00
75d2ffd7f4
lint test utils ( #395 )
2021-01-05 08:50:52 -05:00
d038cca1e1
Verify a workset only exists along with a reboot context ( #378 )
...
Adds the following:
1. Serializes a workset to disk during setup.
2. Upon deserializing a RebootContext, delete the file from disk (We support rebooting once and only once)
3. Check if a workset exists with a RebootContext
1. If True, continuing processing
2. if False, mark the tasks & node as "Done" with appropriate errors via:
1. send WorkerEvent::Done events for each of the tasks in the work set
2. send StateUpdateEvent::Done for the node
2021-01-04 17:51:20 +00:00
3f3193beeb
Use disable_check_debugger on asan integration tests ( #352 )
2020-12-01 10:36:53 -05:00
79cc82098a
Move integration test artifacts into primary source tree ( #336 )
2020-11-24 08:03:01 -05:00
