--sass-binary-path ignored on 'rebuild'

It seems that sass-binary-path is ignored when doing npm rebuild node-sass.
Before opening an issue:

Read the common workarounds in the TROUBLESHOOTING.md
Search for duplicate or closed issues
Validate that it runs with both Ruby Sass and LibSass
Prepare a reduced test case for any bugs
Read the contributing guidelines

When reporting an bug, you must provide this information:

NPM version (npm -v): 3.8.9
Node version (node -v): 6.2.-0
Node Process (node -p process.versions):
{ http_parser: '2.7.0',
node: '6.2.0',
v8: '<IP_ADDRESS>',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '48',
openssl: '1.0.2h' }
Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):
node-sass	3.13.0	(Wrapper)	[JavaScript]
libsass  	3.3.6	(Sass Compiler)	[C/C++]
npm node-sass versions (npm ls node-sass):

When encountering a syntax, or compilation issue:

Open an issue on LibSass. You
may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.

I think this is "by design" since rebuild is used to fall back to locally rebuild the binaries instead of using a prebuilt. Did you have an alternate flow in mind?

No, I think that makes sense. I just came across this while getting node-sass to rebuild using a different binding on an offline CI.

Thanks for the query @cambridgemike


Create payment for invoice

Hello,
i can't create a payement for an invoice because the object PaymentInfo hasn't invoice_id. Do you have a solution or do you explain me how create a payment for an invoice ?
thanks you

Hi
Sorry for missing to describe the invoices property in the sample code.
The CustomerPayment object has the property invoices which is the type of Listto create a payment to the multiple invoices.
The following snippet of code will describes that how to create a partial/full payment for the invoices.
List<Invoice> invoicesToBePaid = new List<Invoice>();
Invoice invoiceToPay = new Invoice()
{
      invoice_id=invoiceId,
      amount_applied=1234.00,
      tax_amount_withheld=0.00,
};
invoicesToBePaid.Add(invoiceToPay);
var newPaymentInfo = new CustomerPayment()
 {
      customer_id = customerId,
      date="2014-02-03",
      amount=1234,
      invoices=invoicesToBePaid,
};

var newCustomerPayment = customerpaymentsApi.Create(newPaymentInfo);
Fell free to contact us on further if you are faced any difficulties or issues.
Thanks&Regards,
Hari Krishna.T.

Thanks you for your help :)
Je reste à votre disposition si vous avez besoin d'informations
supplémentaires.
Bien cordialement,
VivaSoft - Christian Pompier
Intégrateur Google Apps & Zoho CRM
Direction Générale
09-51-91-02-19 / 06-06-50-88-46
www.vivasoft.fr
2015-08-25 8:19 GMT+02:00 Hari Krishna<EMAIL_ADDRESS>
Hi
Sorry for missing to describe the invoices property in the sample code.
The CustomerPayment object has the property invoices which is the type of
Listto create a payment to the multiple invoices.
The following snippet of code will describes that how to create a
partial/full payment for the invoices.
List invoicesToBePaid = new List();
Invoice invoiceToPay = new Invoice()
{
invoice_id=invoiceId,
amount_applied=1234.00,
tax_amount_withheld=0.00,
};
invoicesToBePaid.Add(invoiceToPay);
var newPaymentInfo = new CustomerPayment()
{
customer_id = customerId,
date="2014-02-03",
amount=1234,
invoices=invoicesToBePaid,
};
var newCustomerPayment = customerpaymentsApi.Create(newPaymentInfo);
Fell free to contact us on further if you are faced any difficulties or
issues.
Thanks&Regards,
Hari Krishna.T.
—
Reply to this email directly or view it on GitHub
https://github.com/zoho/books-dotnet-wrappers/issues/1#issuecomment-134493657
.


OnHandleRequest vs. OnMODXInit

It may be that CC predates the Sys Event "OnMODXInit". Wondering if you might consider changing to this event so that CC can be used for MODX_API_MODE mode as well as external loading of modx where a request is not being used.
I have added this event to the plugin on several of my sites but it will be overwritten should there ever be an update of CC.

Just curious, what are you using API Mode for?

Yep, don't think OnMODXInit was around when ClientConfig was first developed in... 2012?
Will need to look into when it was added specifically, but if that's not too recent I don't see a problem changing it in ClientConfig.

@greyskymedia
My use fits more into the external loading category. I have a few accounts where MODX is simply a CMF for a remote non-MODX site or running batch and test scripts that may load modx externally to run a snippet that may depend on System Settings within that should be over loaded with the CC Settings.

Thanks Mark. Ya give it a review. I see nothing in the way myself. There are only a "few lines" apart in where they are triggered.
pretty much the last thing ->initialize() does is invoke 'OnMODXInit' then calls handler and then handler calls OnHandleRequest

I think #115 will take care of this.


Pulse / Snooze

•	Pulse Mode
A channel is shown only once every X days.
•	(Too similar to Snooze?)
•	Snooze Channel
•	Channel is hidden until X days passed (X can be 1 hour, 1 day, 1 week, custom)
•	How to choose Custom?
•	Maybe have a +- sign, that changes from 1h, 1d, 1w, 1m, and a "Custom" button on the side)
•	Incoming messages to that chat do not cause it to show
•	You can view it in a separate Hidden channels list, and Show it (cancels Snooze)
•	Sending a message in a Hidden channel should Unhide it
•	This option should be configurable. In the config, you can make it so sending a message will keep it hidden.

See also #42 for more spec that's similar to this. We might want to merge these features.

Questions from dev :
Q1:Where exactly should the preview be located and what should it look like?
Q2:What should the settings include, can you give an example?

Q3:Add the 'Unhide after sending message' switch to the main menu?
Q4: What does the custom period selection window look like?
Q5:  Where to place the 'Hidden channels' list?
My answers:
I think we should keep it simple so I would ask them what is easier to implement. I guess hide option for defined times with a additional menu *hide conversation will lead to > 1 day,  1 week , forever) ( answers for 1+2)
Q3Since we do not have a real hide I don't know if we want to unhide as a result of message sending
Q4: like a said above
Q5: Don't know

Q3:
We want to unhide by default when sending a message. This should be the default behavior, and there should be a true/false setting in the main menu where you can disable this behavior.
Q4:
The graphics is incorrect. I asked for 4 options:
1 hour
1 day
1 week
custom
Custom is a standard datetime picker that lets you pick a date + time for the duration of the mute.
Q5:
Hidden channels is not relevant right now, please ignore this.

Q1: Add the 'Unhide after sending message' switch to the main menu?
A1: Liat- still want unhide ?

Q2: What does the custom period selection window look like?
examples:
Format № 1

format 2

Q7:What do you think of this format №2?

Q8: “Pulse mode” should hide the channel for X days, then show the channel for one day and then hide it again for X days and keep doing that as long as this feature is on, right?
A8: Liat- Yes
Q9: "Snooze Channel" works like a temporary hide, for a certain amount of time and works once, right?
“Snooze Channel” reminds me of a temporary mute.
A9:
Liat Yes
Estimations:
5hr - pulse mode
5hr - snooze mode
5hr - unhide hidden channel after send message option
? - custom period for pulse popup
? - custom period for snooze popup
? - hidden channels list

A1: Liat- Default should be unhide after sending . within Zen menu add Settings sub menu to include this setting ( optional adding additional settings)

The new menu should include this setting, plus other configurations/settings for other features.

Final decisions regarding implementation of this feature :

upon pressing hide it should act like mute and suggest 3 options : hide for 8 hours, hide for a week hide forever.
Default behavior should be unhide after sending message to a hidden conversation.
Within Zen menu add  we want to add : Settings - a sub menu to include this setting ( optional adding additional settings) . It should state "unhide after sending message to a hidden conversation" ( default Yes).

Hello,Important comment.
The function will only work correctly if the conditions are met:
1.Chat must be open in target.Important condition: as long as we do not have access to high level api WA.
2.Chat must not be empty.Important condition: as long as we don't have access to high level api of WA.

You have opted out of the Custom option. Does this mean we are not adding a time picker dialog or do we need a different format?

For the first iteration of this feature, no time picker.

team estimation :
5hr - time period choose dialog with '8 hours', '1 week', 'forever' options
3hr - adding toogle 'Unhide after sending message to a hidden conversation' option to settings
5hr - unhide after send message
5hr - snooze mode controller

The initial result of the team is 18 hours.
In our experience, the team estimation error is 30%.
18 x 1.3 = 24
3.) Our insurance rate is 30%.
24 x 1.3 = 31
Full optimistic score out of 18 pessimistic out of 31 hours

("החבא")In contact menu upon pressing hide:
"החבא את [converstaion name] למשך:"
8 שעות
שבוע
תמיד
at the bottom( like in mute):
right side for cancel is: בטל
for hiding is: החבא עכשיו
In the zen menu:
unhide after sending message to a hidden conversation" ( default Yes).
in Hebrew:
הראה צ'אט מוחבא לאחר ששלחת הודעה לצ'אט זה ( default yes-> כן)

last estimation:
Task № 30.

Initial estimate 18 hours
the team is wrong 30% of the time.
18 x 1.3 = 24
Our safety stock ratio is 30%
24 x 1.3 = 31
Optimistic estimate 24 hour,pessimistic assessment 31 hours.


Better default window size when running in notebooks

When displaying Rerun in a notebook, the default window size is way too big. We should use a smaller size by default. Pyplot uses a default figsize default: 6.4 x 4.8 inches so I suggest we go with that for starters.
Related (perhaps should be a different issue):
Would be great if the window could be sized to fit the data (when that makes sense) so that we don't show unnecessary "dead" areas

If we show selection/blueprint we need all the space we can get.

Thus: https://github.com/rerun-io/rerun/issues/2288

@jprochazk @jleibs now that you come back fresh from notebook land: Is it realistic for us to do this in the future or are the controls we have for dynamically sizing the widget too limited?

There's no restriction to how we can size the widget. We just need to update DEFAULT_WIDTH and DEFAULT_HEIGHT in notebook.py.


MB-6501 Add aria label to Document Viewer menu

Description
This branch adds an aria-label of Open menu to the menu button in the Document Viewer component.
Reviewer Notes
n/a
Setup
Add any steps or code to run in this section to help others prepare to run your code:
yarn storybook

Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Buttons must have discernible text

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-6501

  Generated by :no_entry_sign: dangerJS against 6abc2e9727fb44c473f05ff1da480f5c7da04071


fix libs.android.shortcut.gradle not found

Unable to replicate, are you sure it's not some issue on your end? Instead of changing build.gradle.kts, could you try specifing the hash in libs.versions.toml in case it was just some cache issue?

Unable to replicate, are you sure it's not some issue on your end? Instead of changing build.gradle.kts, could you try specifing the hash in libs.versions.toml in case it was just some cache issue?

i think i faced this issue sometime ago on a private project... It fixed itself after a few days. and since it's only happening on Github actions, it may be a problem with their SDKs.

Unable to replicate, are you sure it's not some issue on your end? Instead of changing build.gradle.kts, could you try specifing the hash in libs.versions.toml in case it was just some cache issue?

i think i faced this issue sometime ago on a private project... It fixed itself after a few days. and since it's only happening on Github actions, it may be a problem with their SDKs.

In fact, they have deleted the Marven repo, which is why it does not download it. This did not happen to me until I made a version change in my branch.

Unable to replicate, are you sure it's not some issue on your end? Instead of changing build.gradle.kts, could you try specifing the hash in libs.versions.toml in case it was just some cache issue?

i think i faced this issue sometime ago on a private project... It fixed itself after a few days. and since it's only happening on Github actions, it may be a problem with their SDKs.

In fact, they have deleted the Marven repo, which is why it does not download it. This did not happen to me until I made a version change in my branch.

This PR is kind of obsolete now. Can we close it?


Update the contributor's list on Homepage

The contributor's list on homepage of chakra-templates is outdated. It has 32 contributors while the project now has 41 contributors.
Screenshot

The list is fetched from the .all-contributors.rc Should be fixed now. (The Site is build with Next.js and ISR. So it might take a while to display new contributors)


feat: base scaffolding of typescript server module

:tada: This PR is included in version 0.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


wfoverlap: init at 24.08.2020

Standalone version of the WFOverlap program, that is included in the sharc distribution or downloadable at https://sharc-md.org/?page_id=309. It requires some tweaks to build without MKL but works flawless then.
The license is a little bit curious. The entire SHARC repo is under a GPL and the WFOverlap source AND binary is included there. So I would assume a GPL is fine. But in contrast there is also the registration page (see above), with a completely different non-free license.

All done!


Create PotsOfGold.cpp

Please star this repository to show your support, in the meantime I am reviewing your code.

@SaiManasaPappu Why did you close this PR ??

Sorry it was closed due to an error. I starred the repo and am reopening the PR.


Fields are Groups

A lot of cryptographic schemes (some IBEs, ABEs, hash proof systems,  and sumcheck arguments [BCS]) use the abstraction of "modules". Arkworks currently has a nice abstraction, Group,  that essentially implements the operations that we would expect from a module: this is already satisfied in pairing-friendly curves by G1, G2, and PairingOutput.
It'd be really nice if also field implemented this abstraction, so to make possible the realizations of such schemes without having wrappers around the structures. To avoid confusion and lock-out of features of the multiplicative group, perhaps consider renaming Group into AdditiveGroup?. Here's a possible sketch of the steps to achieve this:

[ ] state clearly in the documentation that Groups are additive
[ ] make all Field a Group: this can be first perhaps done in ark-ec with a blanket implementation, to avoid moving code around (hoping this does not break anything)
[ ] move the Group definition into ark-ff for the small operations, and re-assing group-specific methods
[ ] rename Group into AdditiveGroup?

We can move Group to ark-ff without breaking changes, as long as we publicly re-export it from ark-ec anyway. I suggest that we go all the way and just directly make an ark-group crate that is imported by both ark-ff and ark-ec.

@Pratyush @mmagician  what do you think of the above?

I created AdditiveGroup in ark_ff which encapsulates all group operations.
Made Field: AdditiveGroup
Renamed ark_ec::Group into ark_ec::PrimeGroup
Made PrimeGroup: AdditiveGroup

One example where this is useful is this generic sumcheck argument; https://github.com/arkworks-rs/gemini/blob/main/src/herring/
That can avoid all this useless code: https://github.com/arkworks-rs/gemini/blob/main/src/herring/module.rs

I'll look at the actual code later, the idea seems reasonable though 👍🏼

What's the difference between PrimeGroup and AdditiveGroup?

Yes, all field extensions are not PrimeGorup so it wouldn't be possible. Plus, there's all these methods dealing with bit- and byte-representation that are not really fit for non-cyclic groups

removed some code not useful at this stage (implementation of PrimeGroup for PrimeField

That's a good point, makes sense. In that case it might make sense to remove ScalarField from AdditiveGroup, as we might have groups with composite order that is not a prime-power. For example, elliptic curve groups.

ScalarField is needed for any abstract operation you do on them.. should I call it Module instead?

Why do you need a scalar field for operations? Group operations only require Add, Sub, Neg, Zero, One, etc, no?
Do sumcheck arguments require composite-order groups?

yes we need scalar field operations -- and sumcheck arguments require modules (over rings, not necessarily over fields). See e.g. def. 4.1.

bump! @Pratyush @mmagician

Hm my main worry is just that we don't have a way to define a Scalar*Field* for composite order groups. We would need to introduce a Ring abstraction (which I am fine with). However that would make the scope of this PR larger (which I am also fine with)


WIP: set task output directly into the quickfix

Still feeling out what the best API and UX would be. To use it in its current form:
Option 1

After running the task, the "open output in quickfix" action should be available. It will parse the output using the current errorformat and set the results into the quickfix.

Option 2

Add the on_output_parse_errors component to your task
Either add the on_result_diagnostics_quickfix component (to automatically set the quickfix), or use the "set quickfix diagnostics" action once the task has completed.

Thank you for taking an interest. (here from reddit conversation)
This does work, but it adds some extra characters in the output
For example this is the output I get when using :compiler or its extensions
|| /home/ranjith/Software/Workspaces/openFrameworks/myrto/geomShaders/fragmentationCircles/src/ofApp.cpp: In member function ‘virtual void ofApp::setup()’:
src/ofApp.cpp|6 col 5| error: ‘ofEnaleAlphaBlending’ was not declared in this scope; did you mean ‘ofEnableAlphaBlending’?
||     6 |     ofEnaleAlphaBlending();
||       |     ^~~~~~~~~~~~~~~~~~~~

And the entry works the same way any qf entry should, i.e i can press return on that line and it will take me to the file in question.
With overseer for the same task I get this
|| /home/ranjith/Software/Workspaces/openFrameworks/myrto/geomShaders/fragmentationCircles/src/ofApp.cpp: In member function ‘virtual void ofApp::setup()’:
/home/ranjith/Software/Workspaces/openFrameworks/myrto/geomShaders/fragmentationCircles/src/ofApp.cpp|6 col 5|  error: ‘ofEnaleAlphaBlending’ was not declared in this scope; did you mean ‘ofEnableAlphaBlending’?
||     6 |     ofEnaleAlphaBlending();
||       |     ^~~~~~~~~~~~~~~~~~~~
||       |     ofEnableAlphaBlending

Thanks for reporting back! It looks like there's some issues with the stripping of ansi escape codes. There are a lot of CLI tools that try to auto-detect if they are being run in an environment that can handle those, so that might explain the difference (the built-in neovim terminal that we're using would probably be detected as "supports ansi").
Couple of questions:

So I can reproduce it, is this just g++, or are you using a different tool?
Which overseer configuration did you use for this? The on_output_parse_errors component or on_output_write_file with the action?

Quick response, to your questions

Yes I am running g++, technically Gnu Make
this config I am using is on_output_write_file. on_output_parse_errors does not detect these as errors and hence fills nothing in qflist

Just tested this. For the above described use case, it works as I expected! Thank you.
I will also test against other languages and update here

Okay, I've fiddled around with it and the issue was what I expected. g++ provides nice coloring and formatting if it detects that you're running in a terminal, and while we were stripping some of the ansi codes, others were getting through and messing up the parser.
I've updated and simplified a lot of the logic. Both of the options listed in the PR description should work for you now. I would still like to spend a bit of time rethinking the overall story around handling ANSI codes, as I'm not completely happy with a "best effort" sanitization, but I'm out of time. I'll come back to this when I can to try to finalize the API and output parsing decisions, and then merge the PR.

Quick update: I'm going to be off the grid for about a week. This is been in the pending status for longer than I'd like, but it's still on my todo list and I'll come back to it as soon as I'm able.

Quick update: I'm going to be off the grid for about a week. This is been in the pending status for longer than I'd like, but it's still on my todo list and I'll come back to it as soon as I'm able.

For now, I used the logic you created here to create a custom component. Does not take advantage of ANSI suggested colors like you pointed out, but it does what I need. Here
Thanks for all your work

using the current errorformat

It would be great to being able to set custom errorformat for some tasks.


import svg (path must be a string or Buffer)

for me this example doesn't work
https://github.com/zeit/next.js/tree/master/examples/svg-components
npm install babel-plugin-inline-react-svg --save-dev
.babelrc:
{
  "plugins": [
    [
      "module-resolver", {
        "root": ["."],
        "alias": {
          "styles": "./styles"
        },
        "cwd": "babelrc"
    }],
    [
      "wrap-in-js",
      {
        "extensions": ["css$"]
      }
    ],
    ["inline-react-svg"]
  ],
  "presets": [
    "next/babel"
  ],
  "ignore": []
}

and i get
Module build failed:
TypeError: C:/Users/.../src/components/header/View.js: path must be a string or Buffer
    at TypeError (native)
    at Object.fs.openSync (fs.js:641:18)
    at fs.readFileSync (fs.js:509:33)
    at PluginPass.ImportDeclaration (C:\Users\...\node_modules\babel-plugin-inline-react-svg\lib\index.js:63:50)
    at newFn (C:\Users\...\node_modules\babel-traverse\lib\visitors.js:276:21)

tried with multiple sources of svg's. There content looks fine

Just tried the example and it works for me. Maybe there's a windows bug in inline-react-svg?

@flieks I got the same issue, works on mac but not on Debian. Were you able to solve it?

i'm running into the same problem, but the example works for me.

it turns out that the module resolver might be causing some problems with it, i used a relative path for the svg and it works...

@TonyHYK what is the module resolver? Im importing the SVG also with a relative path and it works on my Mac doesn't work on my Ubuntu remote server

https://www.npmjs.com/package/babel-plugin-module-resolver
i'm using the Linux subsystem on windows 10 and my app deployed via now also works fine

So wait, using this module caused this issue? or using it solved it?

the module allowed me to use absolute paths, but was incompatible with svgs, so I went back to using relative paths, obviating the need to rely on the module to resolve the path and the svg loaded correctly

Strange, I already use relative paths and still have this issue.....

Could be because Im using it with the next export?

what do you mean? do you have an example?

Not one that I can share. Its on a private repo. But the use case is very simple. I used the static export example (https://github.com/zeit/next.js/tree/master/examples/with-static-export) as a boilerplate. Added the inline-svg plugin. I then used it like this
`import { PureComponent } from "react";
import OutlineButton from "./outline-button/outline-button-component";
import componentStyles from "./navbar-component.css";
import MondayLogo from "../../../static/monday-logos/monday6-temp-logo.svg";
export default class NavbarComponent extends PureComponent {
render() {
return (

);
}
}`
Hope this helps

ah ok, I'm not too sure then. I think it would be better for someone with more knowledge on babel and next to speak to this...

@aviramga no couldn't fix it. I did copy paste the vector html code inside a wrapper component but this is alot of work if many svg files

Though entirely unrelated to Next.js, I bumped into this error while using babel-inline-react-svg and it turned out to be a stray uppercase character in the filename of the SVG.
OSX's file system preserves case—but will happily load x.svg instead of the specified X.svg I accidentally specified in the import! Most file systems, however...not so happy to play ball.


WIP: use KernelAbstractions

closes #11

Codecov Report
Base: 99.43% // Head: 17.44% // Decreases project coverage by -81.99% :warning:

Coverage data is based on head (cdbf388) compared to base (60057e5).
Patch coverage: 29.24% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #12       +/-   ##
===========================================
- Coverage   99.43%   17.44%   -81.99%
===========================================
  Files           4        5        +1
  Lines         176      235       +59
===========================================
- Hits          175       41      -134
- Misses          1      194      +193

Impacted Files
Coverage Δ

src/AztecDiamonds.jl
13.79% <7.14%> (-85.27%)
:arrow_down:

src/ka.jl
37.17% <37.17%> (ø)

src/show.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/makie.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/dr_path.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: User lists: FAB with an incorrect color

What
AddedbackgroundColor and foregroundColor to FAB on all_user_product_list_page.dart.
Screenshot
Light Mode:

Dark Mode:

Fixes bug(s)

Fixes: #1851

Part of

https://github.com/openfoodfacts/smooth-app/issues/525

Codecov Report

Merging #1868 (022f1e0) into develop (2ea0da3) will decrease coverage by 1.77%.
The diff coverage is 9.64%.

@@            Coverage Diff             @@
##           develop   #1868      +/-   ##
==========================================
- Coverage     8.86%   7.08%   -1.78%
==========================================
  Files          161     174      +13
  Lines         6623    7871    +1248
==========================================
- Hits           587     558      -29
- Misses        6036    7313    +1277

Impacted Files
Coverage Δ

...h_app/lib/cards/category_cards/abstract_cache.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/asset_cache_helper.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/raster_async_asset.dart
0.00% <0.00%> (ø)

...oth_app/lib/cards/category_cards/raster_cache.dart
0.00% <0.00%> (ø)

..._app/lib/cards/category_cards/svg_async_asset.dart
0.00% <0.00%> (ø)

...smooth_app/lib/cards/category_cards/svg_cache.dart
0.00% <0.00%> (ø)

...th_app/lib/cards/data_cards/image_upload_card.dart
0.00% <0.00%> (ø)

...es/smooth_app/lib/cards/data_cards/score_card.dart
4.54% <0.00%> (-0.22%)
:arrow_down:

...t_cards/knowledge_panels/knowledge_panel_card.dart
0.00% <0.00%> (ø)

...knowledge_panels/knowledge_panel_element_card.dart
0.00% <0.00%> (ø)

... and 119 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 534638d...022f1e0. Read the comment docs.

Actually we have multiple FAB's with primary as color, but yes I totally agree we should to this on the Theme layer, we just have to leave out the ones in Search as they have theire own color (white)

Hi @monsieurtanuki @M123-dev ,
Thanks for your comments. I understood your concern of doing the changes at theme level. I'll update the changes with the latest build.


Select Logging Framework

A logging framework should be utilized to decouple EG from any specific logging implementation. The logging framework should:

Support a wide range of logging library implementations, including implementations supported by k8s and k8s-related pkgs. Note that controller-runtime/Istio logging pkgs are built on top of Zap and k8s uses klog.
Provide a lightweight interface that can be used to emit logs.
Be well documented.
Be widely implemented and well maintained by a large, diverse open source community.
The API should restrict logging to just 2-3 types of logs, e.g. info and error.
Provide structured logging.
Provide verbosity levels on info logs as a numerical value instead of semantic meaning such as "warning", "debug", etc. This gives operators an easy way to control the chattiness of log operations.
Integrate with the Cobra, making it easy for EG to use a consistent interface for logging.

EG implementation plan xref: https://github.com/envoyproxy/gateway/issues/60

With the same ideas in mind, we created:
https://github.com/tetratelabs/telemetry
The key point is that it is just an interface with some wrapping logic to support dynamic log levels and Istio style scoped loggers, but allows one to plug their own logging implementations.
This makes it easy for people embedding / building on top of EG libraries to select a different logging library while EG maintainers can write EG packages with logging directives in a consistent manner without worrying about the underlying logging implementation being used by an application binary using EG packages.
A logging Implementation supporting this interface can be found here:
https://github.com/tetratelabs/log/tree/v2
Another interface solution is:
https://github.com/go-logr/logr
However I'm personally not in favor of it due to its V-level interface. It makes it hard in a community project to properly identify verbosity of logs. Making it numeric and open ended allows for dis-synchronization around what a specific log levels verbosity should look like. It puts an extra burden on library authors to think about which level would fit and different authors might have a different sense of what a particular level entails. This is the main reason tetratelabs/telemetry only supports the following output levels to keep it simple:

error (actionable errors / needing alerts)
info (informational / helps provide context)
debug (elevated level for deep debugging / development)

Logr also doesn't take care of allowing scoped loggers with dynamic log level setting.
I have no strong opinion on which logging implementation or output format to use for standard EG, I do have one on which logging interface is used.

dlog is an interface solution that I'd advocate for (disclosure: I'm the original author). It is awfully similar to logr, but

Flattens logr.FromContext(ctx).Info(msg) to dlog.Info(ctx, msg). It was our experience in Emissary/Edge Stack that while ctx was the "main" way to pass the logger around, because you had to extract the logger out of it there was a chance that they would drift, and that this turned out to be an extremely easy mistake for contributors to make.
No V integer; just a few standard log levels: error/warn/info/debug/trace.

I have no strong opinion on which logging implementation or output format to use for standard EG, I do have one on which logging interface is used.

same

I have taken a look at dlog and I would prefer https://pkg.go.dev/github.com/tetratelabs/telemetry#Logger.
Couple of reasons (also see my explanation on what telemetry/logger provides over logr as the same applies to dlog):

A logger itself should not be passed along through context. Typically a log is bound to a library / package / section of your code and holds code point specific context. Letting the request path direct context on its own is tricky.
Request context can be added on top of a code section specific logger while the library author can focus specifically on the context build up from within the package logger (request context will then be augmented to the resulting lines if required)
Package specific loggers allow for zooming in on specific sections of your code to elevate or squelch log lines with runtime level adjustments
typically for Error and Warning logs you'd like to add metrics for aggregated stats on these events. This is made very easy by the telemetry package as it has a metrics interface similar to Istio to automatically drive a count. Driving implementations for the metrics interface could be for instance OpenCensus, OpenTelemetry, or Prometheus.

Note that metrics is an opt in feature. we can choose to do direct OpenTelemetry in our code for metrics purposes without using the telemetry/Metric interface. Using the interface would however allow vendors to choose their implementations just like with logging while we as EG library authors do not need to care about the underlying implementations used in a binary.

Hi, guys.
I wrote a logging library: https://github.com/forgoes/logging
Quicker than Zap, ZeroLog. Benchmark here: https://github.com/forgoes/benchmark-logging
Actually, a logging system is a stream handling system.
My logging library's feature:

quick quick quick;
stream-oriented processing;
parent-child relations between logger;
4....
Sorry that I have not finished the relevant documentation.
Later, I would add more features like:
block logging(for strong consistency scenario);
SafeLogger(you may change the logger's level, handler and so on during runtime, but obviously, SafeLogger will reduce the performance)
...
Just an introduction, I'm really interested in envoy-gateway project.

After discussing in the community meeting yesterday, I'd like to propose that we move forward with using the logr interface for now, with some definition around the usable log levels to address @basvanbeek's concerns.
Can maintainers please cast binding votes here with either reactions or comments, and as always non-binding votes are welcomed.

We discussed this in the community meeting today and agreed that we'll proceed with logr interface for now.

Looking at https://github.com/envoyproxy/gateway/pull/146 I see the usage of https://github.com/go-logr/logr . Major downsides I notice are

the inability to do component level scoping (envoy supports this)
passing the log object around/saving it in some context adding more burden on app devs
it does make sense to continue with logr for now to build out an mvp, hoping we can revisit this post 0.2.0


nuxtServerInit is never called

Using vuex modules in my project and I have the following project structure
store

index.js
auth.js

In my index.js I have the following example
export const state = () => ({
  test: null
})

export const mutations = {
  SET_TEST(state, test){
    console.log('SET_TEST', test)
    state.test = test;
  }
}

export const actions = () => ({
   nuxtServerInit({ commit }, { req }) {
     console.log('calling nuxtServerInit')
      const test = { foo: 'bar'}
      commit('SET_TEST', test)
      if (req.session && req.session.user) {
         commit('auth/SET_USER', req.session.user)
      }
    }
})

and in my auth.js
import axios from 'axios';

export const state = () => ({
  user: null
})

export const mutations = {
  SET_USER(state, user){
    console.log('setUser', user)
    state.user = user || null
  }
}

export const getters = {
  isAuthenticated(state){
    return !!state.user
  },
  loggedUser(state){
    return state.user
  }

}

export const actions = {
  setUser({ commit }, user) {
    commit('SET_USER', user)
  },

  saveUser({state}) {
    return axios.put('/api/user', { user: state.user})
  }
}

But it seems that nuxtServerInit() in never called. I don't see the console.log('calling nuxtServerInit') and the test state and user state are both empty.
Not sure what i'm doing wrong.

What was the issue @frankspin89  ? i'm having a similar issue

@frankspin89 is this fixed?

@kperveen @n-sikka @frankspin89
it works if the actions are exported as an object, not a function.
export const actions =  {
  nuxtServerInit ({ commit }, { req }) {
    console.log('calling nuxtServerInit')
    const test = { foo: 'bar'}
    commit('SET_TEST', test)
    if (req.session && req.session.user) {
      commit('auth/SET_USER', req.session.user)
    }
  }
}


chore: temporarily disabled watsonx tests

[ ] I have added tests that cover my changes.
[ ] If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
[ ] PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
[ ] (If applicable) I have updated the documentation accordingly.

FYI @gyliu513 I needed to disable watson's tests as the requirement of Python >= 3.10 is conflicting with the SDK allowing Python >= 3.8.1
Is there a version of watson that supports Python 3.8?


Alter ID sequence to bigint

TL;DR
Alter ID sequence to bigint.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

I tested the sql on one of our sequences and it worked as expected.
Complete description
As described by https://github.com/flyteorg/flyte/issues/3777, some of the ID sequences are not bigint due to historical reason. It makes sense to use bigint because integer is easy to run out of.
Note that this PR does not try to change cycle in order to keep backward compatibility, and also bigint will practically make that unnecessary.
For reference https://www.postgresql.org/docs/current/sql-altersequence.html
Tracking Issue
Fixes https://github.com/flyteorg/flyte/issues/3777
Follow-up issue
NA

Cc @eapolinario

@honnix , one concern with this change is the possibility of blocking the tables where sequences are not bigints already. We want to minimize downtime, esp. in the case of large tables like task_executions and node_executions.
In the recent past we coordinated tests with other members of the Spotify team. Would it be possible to run a similar test on your side? Sorry for the inconvenience, but database migrations require this extra care.

@eapolinario Good question. We have tested this on our production system and the change took fraction of second. It doesn't do anything to existing sequences, but only changes a single row of the sequence table.

It is worth noting that all the ID columns in different tables are all bigint already, at least in our production database that has been evolving through the past couple of years. It's only the sequence type being inconsistent across different sequences.

Thank you! Please help merge it when suitable.


HWKAGENT-86 remove accounts - require tenant ID to be configured. def…

require tenant ID to be configured. default tenant ID will be "hawkular"

This still needs accounts feature pack stuff to be taken out. I think I need @ppalaga  to help with that. All of this feature pack maven build stuff is magic to me.

do not merge until accounts is removed and nest feature pack replaces it for the itests to work

Closing as the commits from here were adopted and rounded up in #186


JetStream Backoff

Observed behavior
With  code below it looks like the backoff is not in effect.  Also there is no reference anywhere in the source.
Expected behavior
Backoff Setting works
Server and client version
Server: v2.10.11
Client: NATS.Client.JetStream v2.1.2
Host environment
Official NATS docker (latest) with JetStream enabled.
Steps to reproduce
var consumer = await jsContext.CreateOrUpdateConsumerAsync("EVENTS", new ConsumerConfig(consumerName)
{
    DeliverPolicy = ConsumerConfigDeliverPolicy.All,
    FilterSubject = "data.>",
    AckPolicy = ackPolicy,
    AckWait = ackWait,

    MaxDeliver = 5,
    Backoff = new List<long>() { (long) TimeSpan.FromSeconds(1).TotalSeconds, (long)TimeSpan.FromSeconds(2).TotalSeconds }
});

 await foreach (NatsJSMsg<Person> msg in consumer.ConsumeAsync<Person>())
 {
     Console.WriteLine($"Subject: {msg.Subject} Size: {msg.Size}");
     var md = msg.Metadata;
     if (md.HasValue)
     {
        Console.WriteLine($"Num Delivered: {md.Value.NumDelivered} TimeStamp: {md.Value.Timestamp.ToLocalTime()}");
        Console.WriteLine($"Consumer Seq: {md.Value.Sequence.Consumer} Stream Seq: {md.Value.Sequence.Stream}");
     }
     await msg.NakAsync();
 }

it might be nanoseconds, could you try that?
We changed everything to be TimeSpan but missed this one I think 🤔

I have changed to MicroSeconds and there is no difference.  The Re-Delivery went through in quick succession.

I have changed to MicroSeconds and there is no difference. The Re-Delivery went through in quick succession.

it's should be nano .. another x1000

Looking at the source code, it does not seems that Backoff is implemented.

I think this is just passed to the server, I don't think there is anything to implement on client side, is there?

Thanks.   I really missed it.  Nanoseconds did the trick.  It is working as expected.


ci: update to GITHUB_ENV

https://github.com/BurntSushi/ripgrep/commit/13d77ab6463a55ac4ca604076c1da74661b26d69

Thanks @sigmaSd


Formatting Errors

Hey @pvpgamecrash
You have a lot of formatting errors in your code. I'll try to list them all here:
index.html
Here are some errors in your index.html file:

<style> is a descendant of <html>
the <script> pointing to JQuery is a descendant of <html>
<div> is a descendant of <html>
Redundant inline styles in body
Menu uses Unicode, use CSS instead
<center> is obsolete in HTML5, use appropriate CSS instead
height: = 100
<br> should not be used to make space, use appropriate CSS instead
Complete mess of <style> and <script> in the bottom

Blog

Just a copy of a Start Bootstrap theme
Plagiarized posts

Featured

Just a copy of Codyhouse's demo
Doesn't make sense
Uses SCSS, which requires a custom Sass preprocessor, which requires you to use Ruby, which is dynamic/backend, not supported on Github Pages

Stylesheets

Has .zip files, almost no actual custom stylesheets, most of your styles are inline (very inefficient)
Just lots of libraries

Breakout

Copy of MDN's tutorial, no credit given

React.js

Should be used to host Facebook's React library
Uses Node.js, which is backend/server side and cannot be run via Github Pages
No point in having it
No package.json
Your website doesn't require React, it's not a dynamic MVC one page app

params.json

Not required as you don't use a static site generator
Pointless

That's the gist of it, and it only includes major errors, the whole file structure is so hard to understand, you might want to start from scratch. Also, most of this is just a template in which you added your own text, just bits of code copied from sources combined into one, unformatted, inefficient blob.
You might want to actually try learning, instead of copying, it's not a good way of getting into the developer community.

Bro, I copied snippets of code from RipOff Games...

@KingPixil
"<center> is obsolete in html, use appropriate css instead"
In most cases, <center> and </center> tags are better for formatting because they are HTML tags.
Instead of scrolling down to your css or visiting a linked file,  you can wrap HTML around a <center> tag and be done w/ it

If you want us to give credit, just say so.
You don't have to type a long MarkDown comment

##BTW
react.js was just a test
Since GitHub doesn't have a React Compiler, it's pointless

Ok, you might want to improve the code then, I typed the long comment to let you know some things you should fix, never wanted to come across as annoying :smile: I just wanted to help out a little.
You really should make a CSS class, I wrote a blog post on this, <center> is not supported in HTML5, you shouldn't use it at all. See this link.


Make EvaluatePrequential and EvaluateHoldout report all processed samples in the output file

This PR updates the default behavior of EvaluatePrequential when reporting the last measurements and writing the output file. The current implementation updates metrics until the last multiple of n_wait which might be less than the user-defined max_samples, provided that there are enough samples in the stream. For example, if max_samples=2500and n_wait=200 then the last metrics update is performed at sample_count=2400
Expected behavior
Evaluators (prequential and hold out) must include measurements for up to max_samples regardless if n_wait has been reached at the end of the evaluation. In the example above, a final metrics update must be performed for the remaining 100 samples in the stream, to get the final metrics at sample_count=2500.

Checklist
Implementation

[x] Implementation is correct (it performs its intended function).
[x] Code complies with PEP-8 and is consistent with the framework.
[x] Code is properly documented.
[x] PR description covers ALL the changes performed.
[x] Files changed (update, add, delete) are in the PR's scope (no extra files are included).

Tests

[x] New functionality is tested.
[x] Tests are created for the new functionality or existing tests are updated accordingly.
[x] ALL tests pass with no errors.
[x] CI/CD pipelines run with no errors.
[x] Test Coverage is maintained (coverage may drop by no more than 0.2%).

Thanks for the change @smastelini
The same change applies for EvaluateHoldout, can you look into this?

The same change applies for EvaluateHoldout, can you look into this?

Sure! I'll check EvaluateHoldout and update the PR's description.

Does It also impact EvaluatePrequentialDelayed in my PR (pull request #222)?

Does It also impact EvaluatePrequentialDelayed in my PR (pull request #222)?

Hi @fabriciojoc, thanks for pointing that out. I believe that this might impact the delayed evaluator. At least the _update_metrics_delayed method should implement similar changes.

Does It also impact EvaluatePrequentialDelayed in my PR (pull request #222)?

Hi @fabriciojoc, thanks for pointing that out. I believe that this might impact the delayed evaluator. At least the _update_metrics_delayed method should implement similar changes.

Thanks @smastelini! I will consider it when updating my PR, I still have some pending changes to do.

By the way, do you think that it is valid to use tdqm? I discovered this lib this week and maybe this can be useful for the loading bar when processing samples. Sorry for posting this here, but maybe this PR has to do with it (or future work on it).

By the way, do you think that it is valid to use tdqm?

Currently, we have a less sophisticated progress bar. It does the job and no dependencies are required. However, this alternative might be a nice improvement. Please create a new issue to asses how many people would be interested in this feature.

I could not find another place to update the script regarding the metrics' report. @jacobmontiel, could you please check whether am I forgetting something?

This is the line in charge of triggering the test:
https://github.com/scikit-multiflow/scikit-multiflow/blob/e93866ceaa765e36137217ccd7d27af1ab510732/src/skmultiflow/evaluation/evaluate_holdout.py#L288
Looking back at the change, I am now confused about why it works. This is where actual_max_samples is calculated:
https://github.com/scikit-multiflow/scikit-multiflow/blob/e93866ceaa765e36137217ccd7d27af1ab510732/src/skmultiflow/evaluation/evaluate_prequential.py#L277-L279
The original intention of this part of the code was to protect for cases where the stream might contain fewer samples than self.max_samples, which is not the case at hand.

I am now a little bit confused too. :P
From what I can gather, if the stream is infinite or has more available instances than the passed max_samples, the evaluators will limit the auxiliary variable actual_max_samples to the desired limit of samples to process.
The alternative case would be when self.stream.n_remaining_samples() <= self.max_samples. In this situation, the evaluator should process all the available instances. This is actually the scenario which this PR tackles.
Are we missing another corner case?

This is the line in charge of triggering the test:

https://github.com/scikit-multiflow/scikit-multiflow/blob/e93866ceaa765e36137217ccd7d27af1ab510732/src/skmultiflow/evaluation/evaluate_holdout.py#L288

Nice catch! I missed that. Thank you for pointing that out.
If there is not a case we are missing, the following should be the solution:
           if perform_test | (self.global_sample_count >= actual_max_samples):

Are we missing another corner case?

I don't think so.
The csv file is (actually) updated in two cases:

When the buffer size is about to be exceeded
https://github.com/scikit-multiflow/scikit-multiflow/blob/e93866ceaa765e36137217ccd7d27af1ab510732/src/skmultiflow/evaluation/base_evaluator.py#L573-L578

At the end of the evaluation, if and only if there are remaining lines in the buffer
https://github.com/scikit-multiflow/scikit-multiflow/blob/e93866ceaa765e36137217ccd7d27af1ab510732/src/skmultiflow/evaluation/evaluate_prequential.py#L371-L372

Am I missing something?


Use new hash-style access for Redis in robot config template

As mentioned in Lita 4.0 release notes.

The redis configuration attribute is now a hash. Lita 4 will continue to support struct-style access, but only hash-style access will be supported in Lita 5, so you should update now.

Good eye! Thank you.


Don't prompt for interactive login on non-interactive terminals

Fixes #1432

Please note that in the case described in #1432 the deploy fails after a successful upload, because the user is prompted for a message (which should likely default to an empty string in that case).


Fixed custom menu items

Hi
I have fixed some lines in the Navigation.html.twig file, which reference custom menus, and which do not display the properties correctly because they are not called correctly from the template.

I gave it some testing and I can't find how this isn't working. The home page hypertext.artofthesmart.com seems to be working properly without this fix. What makes you feel like it's incorrect in its current state?


Fix gss mapping and only map it in normal mode

When no count is given, use a default count of 1, so the range isn't
negative and no error will be shown.
Fixes #4 by only mapping it in normal mode.

Thanks for the update!


Use comma separation for complex deploy options

Due to how semi-colons are parsed by shells the previous implementation using a semi-colon separated list of values doesn't actually work. I've now changed this to be comma separated instead. As discussed in #104 this is technically a breaking change, but since the old implementation didn't work either I don't think we have to sweat it.
I've also added the clarification discussed in #103 about dotnet publish support being targetted at developers updating their local databases and we suggest using SqlPackage.exe for more advanced scenario's .
Fixes #104
Fixes #103

@ErikEJ Could you have another look here?

@ErikEJ Could you have another look here?


Can you please publish a release for #438?

I need to upgrade my project to fix unit tests?
#437  / #438

Will try to do so later tonight

Released 8.2.7

Thanks!


It's not worked, when i deploy on server.

it's show error.
return new Promise((resolve, reject) =>{
^
SyntaxError: Unexpected token >

Please check if your machine supports "Arrow Function"
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions

@misugijunz would it be better if you add babel transpiler if you want to use ES6 syntax. But IMHO, you could change it to standard function syntax.

@ans-4175 I'll check for it tonite. Thanks.

@misugijunz fixed on my last PR

Ok, I will check and inform you.
On Oct 27, 2016 6:37 AM, "Ahmad Anshorimuslim Syuhada" <
<EMAIL_ADDRESS>wrote:

@misugijunz https://github.com/misugijunz fixed on my last PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nandarustam/fcm-push/issues/16#issuecomment-256520075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM696-2uN14KKoeQ309rCG48s5i0z2dPks5q3_lrgaJpZM4KNuzr
.

was it solved @anujtech46 ? please change it to closed, if it was

@anujtech46 we close this. If you think this case isn't resolved, then you can reopen

why it's still open, any problem?

sorry, i forget to close it.
On Thu, Nov 17, 2016 at 2:12 PM, Ahmad Anshorimuslim Syuhada <
<EMAIL_ADDRESS>wrote:

why it's still open, any problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nandarustam/fcm-push/issues/16#issuecomment-261187831,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM6965s0JfFoDyJvWkzlWFS4AYiubwkVks5q_BN0gaJpZM4KNuzr
.


Could not start Data Curator 2nd time before kill background process from former session

Current Behaviour (for problems)
After starting first time DC and quit I cannot start again.
Look at active process and found 2 Data Curator
Killed them
Can start DC
Application process

Background process I have to kill after Data Curator Quit

Expected Behaviour
Start session without killing background process
Steps to Reproduce

Open Data Curator using the icon
Quit Data Curator
Open Data Curator using the icon

Your Environment

Data Curator version: 0.13.2
Operating System and version: windows 10

V0.14.0 will be out today - the release is currently in draft. Please retest with v0.14.0 when available as this should be fixed

@4estone v0.14.0 ready for your testing

0.14.0 fix issue


[Issue]: Tests fail with cmake 3.31.0

Problem Description
Hi all! I'm packaging the ROCm stack for Arch Linux. While updating to ROCm 6.2.4, I noted that rocm-cmake is not compatible with the current cmake 3.31.0 release. All tests fail:
      Start  1: pass-analyze-gh
 1/32 Test  #1: pass-analyze-gh ......................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-analyze-gh-5bwIw/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-analyze-gh-5bwIw/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-analyze-gh-5bwIw/builds/AiPU9
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  2: pass-analyze
 2/32 Test  #2: pass-analyze .........................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-analyze-Hk38K/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-analyze-Hk38K/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-analyze-Hk38K/builds/0VbV6
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  3: pass-basic-shared
 3/32 Test  #3: pass-basic-shared ....................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-basic-shared-NjjNH/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-basic-shared-NjjNH/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-basic-shared-NjjNH/builds/QKiqP
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  4: pass-basic-static
 4/32 Test  #4: pass-basic-static ....................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-basic-static-ujjRO/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-basic-static-ujjRO/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-basic-static-ujjRO/builds/3mHT6
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  5: pass-headeronly
 5/32 Test  #5: pass-headeronly ......................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-headeronly-lJ21a/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-headeronly-lJ21a/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-headeronly-lJ21a/builds/A8RTv
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  6: pass-libprivate
 6/32 Test  #6: pass-libprivate ......................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-libprivate-EsPvw/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-libprivate-EsPvw/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-libprivate-EsPvw/builds/B04Vi
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  7: pass-rename-compatibility
 7/32 Test  #7: pass-rename-compatibility ............***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rename-compatibility-XpqCg/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rename-compatibility-XpqCg/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rename-compatibility-XpqCg/builds/BPsSM
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  8: pass-rocm-find-program-version
 8/32 Test  #8: pass-rocm-find-program-version .......***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rocm-find-program-version-xPOlB/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rocm-find-program-version-xPOlB/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rocm-find-program-version-xPOlB/builds/5mEIF
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start  9: pass-rocm-join-if-set
 9/32 Test  #9: pass-rocm-join-if-set ................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rocm-join-if-set-wd6Fc/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rocm-join-if-set-wd6Fc/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rocm-join-if-set-wd6Fc/builds/ncYzf
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 10: pass-rocm-list-split
10/32 Test #10: pass-rocm-list-split .................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rocm-list-split-HoqSG/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rocm-list-split-HoqSG/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rocm-list-split-HoqSG/builds/5epjo
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 11: pass-rocm-package-add-dependencies
11/32 Test #11: pass-rocm-package-add-dependencies ...***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rocm-package-add-dependencies-VaYkR/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rocm-package-add-dependencies-VaYkR/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rocm-package-add-dependencies-VaYkR/builds/0BCwT
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 12: pass-rocm-package-setup-component
12/32 Test #12: pass-rocm-package-setup-component ....***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-rocm-package-setup-component-ouGt5/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-rocm-package-setup-component-ouGt5/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-rocm-package-setup-component-ouGt5/builds/RXyhr
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 13: pass-simple-build-id
13/32 Test #13: pass-simple-build-id .................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-build-id-uajp1/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-build-id-uajp1/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-build-id-uajp1/builds/BELew
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 14: pass-simple-prefix
14/32 Test #14: pass-simple-prefix ...................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-prefix-doMcI/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-prefix-doMcI/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-prefix-doMcI/builds/CfJIJ
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 15: pass-simple-rocmversion-env
15/32 Test #15: pass-simple-rocmversion-env ..........***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-rocmversion-env-hUM4c/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-rocmversion-env-hUM4c/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-rocmversion-env-hUM4c/builds/tlHpP
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 16: pass-simple-soversion-env
16/32 Test #16: pass-simple-soversion-env ............***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-env-njpRi/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-env-njpRi/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-env-njpRi/builds/XOSi4
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 17: pass-simple-soversion
17/32 Test #17: pass-simple-soversion ................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-rxPwo/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-rxPwo/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-soversion-rxPwo/builds/2TGnS
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 18: pass-simple-test-package
18/32 Test #18: pass-simple-test-package .............***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-test-package-vbUqi/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-test-package-vbUqi/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-test-package-vbUqi/builds/pEeiP
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 19: pass-simple-test
19/32 Test #19: pass-simple-test .....................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-test-leLGF/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-test-leLGF/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-test-leLGF/builds/x3JRy
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 20: pass-simple
20/32 Test #20: pass-simple ..........................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-simple-694wx/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-simple-694wx/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-simple-694wx/builds/heaQd
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 21: pass-version-atag-short
21/32 Test #21: pass-version-atag-short ..............***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-version-atag-short-4S3zl/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-version-atag-short-4S3zl/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-version-atag-short-4S3zl/builds/6sNVA
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 22: pass-version-atag
22/32 Test #22: pass-version-atag ....................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-version-atag-AXJE9/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-version-atag-AXJE9/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-version-atag-AXJE9/builds/Fzlsc
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 23: pass-version-nogit
23/32 Test #23: pass-version-nogit ...................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-version-nogit-UU9jZ/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-version-nogit-UU9jZ/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-version-nogit-UU9jZ/builds/tEUKt
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 24: pass-version-patch
24/32 Test #24: pass-version-patch ...................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-version-patch-rKkU0/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-version-patch-rKkU0/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-version-patch-rKkU0/builds/jTs6n
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 25: pass-version
25/32 Test #25: pass-version .........................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-version-Ey7hF/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-version-Ey7hF/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-version-Ey7hF/builds/qzM9V
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 26: pass-wrapper-nowarn
26/32 Test #26: pass-wrapper-nowarn ..................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-wrapper-nowarn-44BeR/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-wrapper-nowarn-44BeR/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-wrapper-nowarn-44BeR/builds/8qaG6
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 27: pass-wrapper
27/32 Test #27: pass-wrapper .........................***Failed    0.03 sec
CMake Deprecation Error at CMakeLists.txt:5 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- rocm-cmake: Set license file to /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/LICENSE.
-- Configuring incomplete, errors occurred!
CMake Error at /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:94 (message):
  Process failed: COMMAND /usr/bin/cmake -Werror=dev -D
  CMAKE_MAKE_PROGRAM=/usr/bin/make -G Unix Makefiles
  -DCMAKE_PREFIX_PATH=/build/rocm-cmake/src/build/test/tmp/pass-wrapper-u6Pd2/usr
  -DCMAKE_INSTALL_PREFIX=/build/rocm-cmake/src/build/test/tmp/pass-wrapper-u6Pd2/usr
  -DROCM_ERROR_TOOLCHAIN_VAR=On -DROCM_SYMLINK_LIBS=OFF
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/../ WORKING_DIRECTORY
  /build/rocm-cmake/src/build/test/tmp/pass-wrapper-u6Pd2/builds/11PT4
Call Stack (most recent call first):
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:114 (test_exec)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:139 (configure_dir)
  /build/rocm-cmake/src/rocm-cmake-rocm-6.2.4/test/test.cmake:175 (install_dir)

      Start 28: fail-basic-shared
28/32 Test #28: fail-basic-shared ....................   Passed    0.03 sec
      Start 29: fail-rocm-find-program-version
29/32 Test #29: fail-rocm-find-program-version .......   Passed    0.03 sec
      Start 30: fail-toolchain-var
30/32 Test #30: fail-toolchain-var ...................   Passed    0.03 sec
      Start 31: fail-wrapper-error
31/32 Test #31: fail-wrapper-error ...................   Passed    0.03 sec
      Start 32: fail-wrapper
32/32 Test #32: fail-wrapper .........................   Passed    0.03 sec

16% tests passed, 27 tests failed out of 32

Total Test time (real) =   0.89 sec

The following tests FAILED:
	  1 - pass-analyze-gh (Failed)
	  2 - pass-analyze (Failed)
	  3 - pass-basic-shared (Failed)
	  4 - pass-basic-static (Failed)
	  5 - pass-headeronly (Failed)
	  6 - pass-libprivate (Failed)
	  7 - pass-rename-compatibility (Failed)
	  8 - pass-rocm-find-program-version (Failed)
	  9 - pass-rocm-join-if-set (Failed)
	 10 - pass-rocm-list-split (Failed)
	 11 - pass-rocm-package-add-dependencies (Failed)
	 12 - pass-rocm-package-setup-component (Failed)
	 13 - pass-simple-build-id (Failed)
	 14 - pass-simple-prefix (Failed)
	 15 - pass-simple-rocmversion-env (Failed)
	 16 - pass-simple-soversion-env (Failed)
	 17 - pass-simple-soversion (Failed)
	 18 - pass-simple-test-package (Failed)
	 19 - pass-simple-test (Failed)
	 20 - pass-simple (Failed)
	 21 - pass-version-atag-short (Failed)
	 22 - pass-version-atag (Failed)
	 23 - pass-version-nogit (Failed)
	 24 - pass-version-patch (Failed)
	 25 - pass-version (Failed)
	 26 - pass-wrapper-nowarn (Failed)
	 27 - pass-wrapper (Failed)
Errors while running CTest
make[3]: *** [CMakeFiles/check.dir/build.make:70: CMakeFiles/check] Error 8
make[2]: *** [CMakeFiles/Makefile2:228: CMakeFiles/check.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:235: CMakeFiles/check.dir/rule] Error 2
make: *** [Makefile:214: check] Error 2

Operating System
Arch Linux
CPU
AMD EPYC 9454P
GPU
gfx000
ROCm Version
ROCm 6.2.3
ROCm Component
rocm-cmake
Steps to Reproduce
With current cmake,
cmake -B build
cmake --build build
cmake --build build --target check

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

Hi @tpkessler, thanks for the report. I've created an internal ticket to address these errors.

Hi @tpkessler, thanks for reporting the issue. This problem probably would affect CMake versions >= 3.27. Seems like the culprits are

CMake is deprecating cmake_minimum_requried < 3.10, which was set to 3.5 or 3.6 in many of the cmake files in the tests.
[CMake policy 0079 Old will by default generate a deprecation error] (https://cmake.org/cmake/help/latest/policy/CMP0079.html)

All tests except for the ones involving policy 0079 passed after setting the minimum required versions to 3.10. Running cmake with -Wno-deprecated and -Wno-error=deprecated should be able to by pass these issues for now. Thanks!

Thanks! I fixed my build by increasing minimum version of all cmake files to 3.10 and patching the test runner,
--- rocm-cmake-rocm-6.2.4/test/test.cmake.bak	2024-11-23 09:36:53.749629000 +0100
+++ rocm-cmake-rocm-6.2.4/test/test.cmake	2024-11-23 09:37:42.573123886 +0100
@@ -111,7 +111,7 @@
     if(NOT EXISTS ${BUILD_DIR})
         file(MAKE_DIRECTORY ${BUILD_DIR})
     endif()
-    test_exec(COMMAND ${CMAKE_COMMAND} -Werror=dev ${ADDITIONAL_CONFIGURE_ARGS} -DCMAKE_PREFIX_PATH=${PREFIX}
+    test_exec(COMMAND ${CMAKE_COMMAND} -Wno-deprecated -Wno-error=deprecated ${ADDITIONAL_CONFIGURE_ARGS} -DCMAKE_PREFIX_PATH=${PREFIX}
                       -DCMAKE_INSTALL_PREFIX=${PREFIX} -DROCM_ERROR_TOOLCHAIN_VAR=On ${PARSE_CMAKE_ARGS} ${DIR}
               WORKING_DIRECTORY ${BUILD_DIR})
     foreach(TARGET ${PARSE_TARGETS})


crates.io release and current state

This create looks very nice, I winder why is it not published to crates.io? Is it because it's not stable/mature enough?
I'd like to use it as a library in my cli tool, but I am not sure if it's ready yet.

Thanks for your interest in this project! I was indeed waiting for this project to be more mature before publishing it (most notably having actual support for standard EFI variables such as BootOrder/BootNext without having to manipulate their raw binary values), but the basic read/write/list functionality is here (efivar crate) and works on Linux and Windows. If you're interested I could update the dependencies and publish it in that state as a first 0.1.0 version.

That would be great, thanks!