[ cb ] Remove penalties from Greedy config (#896) #1
Triggered via push
September 26, 2024 10:47
andrei-kochin
Status
Cancelled
Total duration
1d 5h 21m 7s
Artifacts
–
causal_lm_cpp.yml
on: push
Matrix: cpp-beam_search_causal_lm-ubuntu
cpp-multinomial-greedy_causal_lm-ubuntu
0s
cpp-greedy_causal_lm-windows
0s
cpp-beam_search_causal_lm-Qwen-7B-Chat
0s
cpp-beam_search_causal_lm-Qwen1_5-7B-Chat
0s
cpp-beam_search_causal_lm-Phi-2
0s
cpp-beam_search_causal_lm-notus-7b-v1
0s
cpp-speculative_decoding_lm-ubuntu
0s
cpp-prompt_lookup_decoding_lm-ubuntu
0s
cpp-Phi-1_5
0s
cpp-greedy_causal_lm-redpajama-3b-chat
0s
cpp-chat_sample-ubuntu
13m 0s
cpp-continuous-batching-ubuntu
0s
cpp-continuous-batching-windows
0s
cpp-continuous-batching-macos
20m 57s
ci/gha_overall_status_causal_lm
0s
Annotations
11 errors and 5 warnings
|
cpp-speculative_decoding_lm-ubuntu
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-multinomial-greedy_causal_lm-ubuntu
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-beam_search_causal_lm-Qwen1_5-7B-Chat
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-beam_search_causal_lm-Qwen-7B-Chat
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-beam_search_causal_lm-Phi-2
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-continuous-batching-ubuntu
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-prompt_lookup_decoding_lm-ubuntu
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-beam_search_causal_lm-notus-7b-v1
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-greedy_causal_lm-redpajama-3b-chat
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
cpp-Phi-1_5
Canceling since a higher priority waiting request for 'causal_lm_cpp-refs/heads/master' exists
|
|
ci/gha_overall_status_causal_lm
Process completed with exit code 1.
|
|
cpp-beam_search_causal_lm-ubuntu (./build/samples/cpp/beam_search_causal_lm/beam_search_causal_lm)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
cpp-chat_sample-ubuntu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
cpp-beam_search_causal_lm-ubuntu (python ./samples/python/beam_search_causal_lm/beam_search_causa...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
cpp-continuous-batching-macos
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
cpp-continuous-batching-macos
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|